Potential fix for code scanning alert no. 1: Workflow does not contain permissions#362
Draft
Potential fix for code scanning alert no. 1: Workflow does not contain permissions#362
Conversation
…n permissions Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com> Signed-off-by: Kurt Garloff <kurt@garloff.de>
garloff
commented
Feb 4, 2026
Member
Author
garloff
left a comment
garloff
left a comment
There was a problem hiding this comment.
Honestly, it's hard to judge for me.
I understand that gh-manager needs the ability to create repositories and to manage users -- and I don't find any matching permissions
Any gh pro wants to provide advice?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Potential fix for https://github.com/SovereignCloudStack/github-manager/security/code-scanning/1
To fix this issue, explicitly declare a
permissionsblock to restrict the default power of the GITHUB_TOKEN for this workflow. Place it at the root level (top of the YAML, below thename:andon:blocks) so it applies to all jobs unless overridden. Since no steps require write access via the GITHUB_TOKEN, settingpermissions: { contents: read }ensures only read access to repository contents, following the principle of least privilege.Change to make:
.github/workflows/manage-github-repositories.yml(aftername:or afteron:), add:Suggested fixes powered by Copilot Autofix. Review carefully before merging.